Skip to content

Conversation

@leolost2605
Copy link
Member

@leolost2605 leolost2605 commented Feb 27, 2025

I've thought of this a while ago but wasn't sure how the UI would look like. Now I think it might be best as a context menu for the dock workspaces.

What this allows is to mark certain workspaces as "permanent". This means they wont be removed once there are no more windows on them. They will also already be available when starting.
This allows for a kind of hybrid between static and dynamic workspaces. If you don't mark anything as permanent behavior doesn't change compared to main.

The reason for this is that I found having static workspaces more useful for certain situations. For example currently when studying I like to have my first workspace for a browser window with misc stuff and my second workspace for the stuff that I need for my next exam and my third workspace for the stuff that I need for the exam after that. But sometimes I just want to start with the last one but after 5 minutes I want to google some unrelated stuff which I usually do on the first workspace. But now I have to open the browser on the second workspace and reorder. Building muscle memory like that (e.g. super + number for the workspace) doesn't work either. And when I close the browser because I've opened 100 tabs and my memory is getting full I will have to do the same thing again because the workspace got removed again.
On the other hand I don't want full static workspaces because e.g. inserting a new workspace when going fullscreen or adding new "temporary" workspaces for some fun stuff i want to do now when taking a break is really useful.

I'm not sure this is in line with the elementary multitasking model (though I don't see why not but might be missing something) so this is just a proposal :)

To test this I'd recommend setting the dconf key to the number of workspaces that should be permanent and logging out and in again. Alternatively you can use dspy and set any workspace that you want as permanent.

Let me know your thoughts, suggestions and improvements :)

Fixes #433

@leolost2605 leolost2605 requested a review from a team February 27, 2025 20:43
@lenemter lenemter added the Conflicts Has conflicts with the target branch label Mar 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Conflicts Has conflicts with the target branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support static workspaces

3 participants